POWER MANAGEMENT OF AN IoT TRACKER

ABSTRACT

Techniques described herein may be used to conserver battery power of an Internet of Things (IoT) tracker by increasing the overall amount of time that the IoT tracker is in a battery conservation mode (a sleep mode, a Power Save Mode (PSM), etc.). An IoT tracker may implement a battery conservation policy that may include instructions that cause the IoT tracker to monitor certain conditions, determine when the conditions satisfy a particular trigger, and implement a battery conservation mode in response to those conditions. Examples of such conditions may include (1) the IoT tracker being close to a user device designated to track the location of the IoT tracker, (2) identifying that a current time and day are associated with a pre-selected schedule for disabling tracking services, (3) the IoT tracker being located within a particular geographic area, and more.

CROSS-REFERENCE TO RELATED APPLICATION

This Application is a Continuation of U.S. patent application Ser. No.15/154,894, filed on May 13, 2016, titled “POWER MANAGEMENT OF AN IoTTRACKER,” the contents of which are herein incorporated by reference intheir entirety.

BACKGROUND

Wireless telecommunication networks often include user equipments (UEs)that connect to Radio Access Networks (RANs) of the wirelesstelecommunication network. The UE may include user devices, such assmartphones, tablet computers, etc., and Internet of Things (IoT)devices (also referred to as Machine Type Communication (MTC) devicesand Machine-to-Machine (M2M) devices). An example of an IoT device mayinclude Category 1 (CAT 1) trackers (also referred to as an IoTtracker). IoT trackers may be used, for example, to communicate with awireless telecommunications network to track the location of the IoTtracker itself and/or an object to which an IoT tracker is attached. Dueto the mobile nature of an IoT tracker, an IoT tracker may often includea small batter powered device.

In operation, an IoT tracker may periodically determine a currentgeographic location (e.g., via Global Positioning System (GPS), ObservedTime Difference of Arrival, etc.) of the IoT tracker and provide thelocation to a user device, or another device, via the wirelesstelecommunication network. In this manner, the movements of an IoTtracker, and hence the movement of the object to which the IoT trackeris attached, may be monitored.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present disclosure will be readily understood by thefollowing detailed description in conjunction with the accompanyingdrawings. To facilitate this description, like reference numerals maydesignate like structural elements. Embodiments of the disclosure areillustrated by way of example and not by way of limitation in thefigures of the accompanying drawings.

FIG. 1 illustrates an example overview of an implementation describedherein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 3 illustrates an example process for implementing a batteryconservation policy;

FIG. 4 illustrates an example of instructions and information that maybe included in a battery conservation policy;

FIG. 5 illustrates an example for implementing a proximity-based batteryconservation policy;

FIG. 6 illustrates an example schedule that may be used to implement aschedule-based battery conservation policy;

FIG. 7 illustrates an example of using geo-fencing to implement abattery conservation policy;

FIG. 8 illustrates an example of an activity-based battery conservationpolicy;

FIG. 9 illustrates an example process for generating a batteryconservation policy; and

FIG. 10 is a diagram of example components of a device.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. It is to be understood that other embodiments maybe utilized and structural or logical changes may be made withoutdeparting from the scope of the present disclosure. Therefore, thefollowing detailed description is not to be taken in a limiting sense,and the scope of embodiments in accordance with the appended claims andtheir equivalents.

A UE, such as an IoT tracker device, may rely on a power source, such asa battery, in order to function. Once the battery is depleted, the IoTtracker may cease to operate until the battery is recharged or replaced.In order to preserve battery power, the IoT tracker may periodicallyenter into battery conservation mode, which may include a sleep mode, aPower Save Mode (PSM), etc. Since location services and other types ofnetwork services often require a significant amount of power, a batteryconservation mode may be directed at limiting communications between theIoT tracker and external networks (as opposed to, for example, processesthat are completely internal to the IoT device).

As used herein, a sleep mode may include a mode of operation where anIoT tracker communicates with the network periodically. An example of asleep mode may include enhanced discontinuous reception (eDRX) mode. Insuch a mode, the IoT tracker may notify the network when the IoT trackerwill listen for communications from the network to find out aboutwhether there is important information for the IoT tracker to receive.Between “listening” moments, the IoT tracker may disable receiverfunctions in order to conserver power. During a listening moment, theIoT tracker may re-enable the receiver functions and listen fornotification about information for the IoT tracker to receive/obtainfrom the network. If such a notification is not received, the IoTtracker may reenter the sleep mode. However, if such a notification isreceived, the IoT tracker may communicate with the network in order toreceive the information. In a sense, therefore, the network may causethe IoT tracker to awaken from a sleep mode by informing the IoT device,during “listening” moments, about information that is available from thenetwork.

By contrast, when an IoT tracker enters into a PSM, the IoT tracker mayremain registered with the network (e.g., have no need to re-attach tothe network, reestablish packet data network (PDN) connections, etc.),however, the IoT tracker may be unavailable to the network for theduration of the PSM. For instance, the IoT tracker may discontinuemonitoring for paging signals from the network and turn off allnon-critical functionally. Some of the disabled features or functionsmay include location services, mobile data services, and other servicesthat tend to use a lot of battery power.

Before entering the PSM, the IoT tracker may notify the network abouthow long the PSM will last, and the IoT tracker may stay in the PSMuntil the stated duration has expired or a user provides a command forthe IoT tracker to exit the PSM. While in the power save mode, thenetwork may not prompt or cause the IoT tracker to exit the PSM. Oncethe IoT tracker exits the PSM, the features and/or processes that weredisabled as a result of entering into the PSM may be resumed (regardlessof whether the network has informed the IoT tracker of importantinformation that the network has for the IoT tracker). In someimplementations, the IoT tracker may enter into a PSM after being in anormal idle mode for a period of time (e.g., a mode of operation thatmay be limited to rudimentary operations such as monitoring for pagingsignals from the network).

Techniques described herein may be used to conserver battery power of anIoT tracker by increasing the overall amount of time that the IoTtracker is in a battery conservation mode (a sleep mode, a PSM, etc.).For instance, the techniques described herein may enable IoT trackers toimplement battery conservation policies that may include instructionsthat cause the IoT tracker to monitor certain conditions, determine whena particular condition, trigger, or threshold has been reached withrespect to those conditions, and implement an appropriate batteryconservation mode in response to those conditions. Examples of suchconditions may include (1) the IoT tracker being close to a particulardevice (e.g., a user device) designated to track the location of the IoTtracker, (2) identifying that a current time and day are associated witha pre-selected schedule for disabling tracking services, (3) the IoTtracker being located within a particular geographic area (e.g., alocation where tracking is unnecessary), and more.

FIG. 1 illustrates an example overview of an implementation describedherein. As shown, a user device (e.g., a smartphone, a tablet computer,etc.) may communicate, via a Radio Access Network (RAN) with a serverthat provides IoT tracker services. The user device may register, withthe server, an IoT tracker that is installed in a vehicle, and may alsodefine battery conservation policies for the IoT tracker (at 1). Thebattery conservation policies may be provided, via the RAN, to the IoTtracker (at 2). The IoT tracker may implement the battery conservationpolicies in order to conserve battery power and, thereby, extend theoverall life of the battery (at 3).

As described herein, a battery conservation policy may include rules andinstructions to conserve the power of a battery of an IoT tracker by,for example, causing the IoT tracker to enter into a batteryconservation mode (e.g., a sleep mode, a PSM, etc.) in response tocertain conditions that are specified by the battery conservationpolicy. FIG. 1 provides a list of examples of battery conservationpolicies (at 4). In one example, a battery conservation policy mayinclude a proximity-based policy, such that the IoT tracker may enterinto a battery conservation mode whenever a particular device (such as auser device registered to track the IoT tracker) is within closeproximity of the IoT tracker. As another example, a battery conservationpolicy may include a schedule-based policy, where the IoT tracker mayenter into a battery conservation mode at a particular time (e.g., whilea user or device to which the IoT tracker is attached is at school,work, church, etc.).

In another example, a user-initiated location reporting policy may causethe IoT tracker to remain in a battery conservation mode unless/until auser inputs a command for the IoT tracker to determine and/orcommunicate the location of the IoT tracker. In yet another example, ageo-fencing policy may be used to cause the IoT tracker to enter into abattery conservation mode whenever the IoT tracker is located inside ofa pre-defined geographic area, such as a home, a neighborhood, acommercial center, a city, a county, etc. A battery conservation policymay also include an activity-based policy, where the IoT tracker willmonitor whether the IoT tracker is moving. When the IoT tracker isstationary, the IoT tracker may enter into a battery conservation mode;however, when the IoT tracker begins moving, the IoT tracker may exitthe battery conservation mode and resume with determining andcommunicating the location of the IoT tracker.

An example of a battery conservation policy may include postponing theimplementation of a battery conservation mode when the IoT tracker isconnected to an external power source. For instance, the IoT tracker mayhave a local battery designated exclusively to the IoT tracker. When theIoT tracker must use the local battery, the IoT tracker may implement abattery conservation policy. However, when the IoT tracker beginsoperating based on an external power source, such as the battery of avehicle, an AC electrical outlet, etc., the IoT tracker may not enterinto a battery conservation mode because such a mode may not bebeneficial to conserving the power of the battery of the IoT tracker.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. Environment 200 mayinclude UEs (e.g., user devices 210, IoT trackers 220, etc.), a wirelesstelecommunications network, external network 250, and IoT trackerservices device 260. The wireless telecommunications network may includea Long-Term Evolution (LTE) network and EPC 240. The LTE network mayinclude a RAN consisting of one or more base stations, some or all ofwhich may take the form of enhanced node Bs (eNBs) 230, via which UEsmay communicate with the EPC 240.

User device 210 may include a portable computing and communicationdevice, such as a personal digital assistant (PDA), a smart phone, acellular phone, a laptop computer with connectivity to the wirelesstelecommunications network, a tablet computer, etc. User device 210 mayalso include a non-portable computing device, such as a desktopcomputer, a consumer or business appliance, or another device that hasthe ability to connect to a RAN of the wireless telecommunicationsnetwork. User device 210 may also include a computing and communicationdevice that may be worn by a user (also referred to as wearable devices)such as a watch, a fitness band, a necklace, glasses, an eyeglass, aring, a belt, a headset, or another type of wearable device.

As shown, user device 210 may include a tracking application thatenables user device 210 to track the geographic locations of IoTtrackers 220 that are registered to user device 210. The trackingapplication may be downloaded and installed from IoT tracker servicesdevice 260 or from another source. User device 210 may register IoTtrackers 220 by accessing a web portal, via the tracking application oranother type of application (e.g., a web browser), hosted by IoT trackerservices device 260. Similarly, by communicating with IoT trackerservices device 260, user device 210 may create battery conservationpolicies, delete battery conservation policies, and/or edit batteryconservation policies that are provided to, and implemented by, IoTtrackers 220.

In some implementations, IoT tracker 220 may include a stand-aloneMachine-to-Machine (M2M) device or Machine-Type-Communication (MTC)device that may be inserted into, attached to, installed in, etc.,another object in order to track the geographic locations of thatobject. Examples of such an object may include an inanimate object, suchas a vehicle, a package, an article of clothing (e.g., a purse, a pantpocket, a backpack, etc.), a user device, etc., and/or an animateobject, such as people and/or animals. In some implementations, IoTtracker 220 may be attached to one object, such as a collar, and then(in turn) attached to another object, such as a dog (via the collar), inorder to track the movements of the dog.

IoT tracker 220 may include a wireless computing and communicationdevice that may be designed to collect certain types of information(e.g., geographic location information) and send the information to adestination device (e.g., IoT tracker services device 260, user device210, or another device) via the wireless telecommunications network. Insome implementations, IoT tracker 220 may send the information directlyto user device 210 via a different network/connection, such as aBluetooth connection, a WiFi network to which IoT tracker 220 and userdevice 210 are connected, etc.

As shown, IoT tracker 220 may include battery conservation software,which may enable IoT tracker 220 to download, install, and implementbattery conservation policies from IoT tracker services device 260. Insome implementations, the battery conservation software may also, oralternatively, enable user device 210 to access IoT tracker 220 (e.g.,via a configuration interface made available by IoT tracker 220) inorder to create battery conservation policies, delete batteryconservation policies, and/or edit existing battery conservationpolicies. As described above, a battery conservation policy may includeinformation and instructions for IoT tracker 220 to monitor certainconditions, identify when a trigger or threshold has been reached, andimplement a battery conservation mode (e.g., a sleep mode, a PSM, etc.)in response to the trigger being satisfied.

eNB 230 may include one or more network devices that receives,processes, and/or transmits traffic destined for and/or received fromuser device 210 and/or IoT tracker 220 via an air interface. eNB 230 maybe connected to a network device, such as site router, that functions asan intermediary for information communicated between UEs and EPC 240. Insome implementations, eNB 230, EPC 240, and/or the external network mayassist IoT tracker 220 in determining a geographic location of IoTtracker 220 (e.g., via GPS, Observed Time Difference of Arrival, etc.).

EPC 240 may include one or more network devices, some or all of whichare similar to network devices provide in a traditional core network ofa 3rd Generation Partnership Project (3GPP) Communication Standard.Examples of such network devices may include Serving Gateways (SGWs), aPDNs Gateway (PGWs), Mobility Management Entities (MMEs), HomeSubscriber Servers (HSSs), and more. In some implementations, EPC 240may be connected to one or more additional networks, such as an InternetProtocol (IP) Multimedia Subsystem, Broadcast Multicast networks, andother networks.

External networks 250 may include one or more wired and/or wirelessnetworks. For example, network 240 may include another cellular network(e.g., a second generation (2G) network, a third generation (3G)network, a fourth generation (4G) network, a fifth generation (5G)network, another LTE network, a global system for mobile (GSM) network,a code division multiple access (CDMA) network, an evolution-dataoptimized (EVDO) network, or the like), a public land mobile network(PLMN), and/or another network. Additionally, or alternatively, network240 may include a local area network (LAN), a wireless LAN (WLAN), awide area network (WAN), a metropolitan network (MAN), the PublicSwitched Telephone Network (PSTN), an ad hoc network, a managed IPnetwork, a virtual private network (VPN), an intranet, the Internet, afiber optic-based network, and/or a combination of these or other typesof networks.

IoT tracker services system 260 may include one or more computingdevices, such as a server device or a collection of server devices,capable of providing support and other services to user device 210 andIoT tracker 220. For instance, user device 210 may download and installone or more software applications from IoT tracker services system 260,which may enable user device 210 to perform one or more of theoperations described herein. Examples of such operations may includeregistering IoT trackers 220, creating battery conservation polices,receiving tracking information from IoT trackers 220, etc. Similarly,IoT tracker services system 260 may enable IoT tracker 220 to downloadand install one or more software applications from IoT tracker servicessystem 260 or from another device, which may enable IoT tracker 220 toperform one or more of the operations described herein. Examples of suchoperations may include downloading, creating, and/or implementingbattery conservation policies as described herein. IoT tracker servicessystem 260 may also provide facilities to manage the operation of IoTtrackers 220, for example via software applications installed in userdevices 210 and/or through user interfaces and communications interfacesprovided by IoT tracker services system 260 (e.g., web pages, webservices, application programming interfaces (APIs), etc.).

The quantity of devices and/or networks, illustrated in FIG. 2, isprovided for explanatory purposes only. In practice, environment 200 mayinclude additional devices and/or networks; fewer devices and/ornetworks; different devices and/or networks; or differently arrangeddevices and/or networks than illustrated in FIG. 2. For example, whilenot shown, environment 200 may include devices that facilitate or enablecommunication between various components shown in environment 200, suchas routers, modems, gateways, switches, hubs, etc. Alternatively, oradditionally, one or more of the devices of environment 200 may performone or more functions described as being performed by another one ormore of the devices of environments 300. Additionally, the devices ofenvironment 200 may interconnect with each other and/or other devicesvia wired connections, wireless connections, or a combination of wiredand wireless connections. In some implementations, one or more devicesof environment 200 may be physically integrated in, and/or may bephysically attached to, one or more other devices of environment 200.Also, while “direct” connections are shown in FIG. 2 between certaindevices, some devices may communicate with each other via one or moreadditional devices and/or networks.

FIG. 3 illustrates an example process 300 for implementing a batteryconservation policy. In some implementations, process 300 may beperformed by IoT tracker 220.

As shown, process 300 may include receiving a battery conservationpolicy (block 310). For example, IoT tracker 220 may receive a batteryconservation policy from IoT tracker services device 260. As mentionedabove, a user of user device 210 may have created the batteryconservation policy. Alternatively, the battery conservation policy mayinclude a battery conservation policy made available to some or all IoTtracker devices 220 by default (e.g., the policy may be provisioned forthe IoT tracker during the manufacture of the IoT tracker).

The battery conservation policy may include instructions for IoT tracker220 to monitor certain conditions, identify when a trigger or thresholdhas been reached, and implement a prescribed battery conservation mode(e.g., a sleep mode, a PSM, etc.). For example, the battery conservationpolicy may include instructions for IoT tracker 220 to monitor a levelof activity of the IoT tracker 220, determine whether the level ofactivity falls below a particular threshold, and enter into a sleep modeor a PSM in response to the activity level falling below the threshold.Several examples of the instructions and information that may define abattery conservation policy are discussed below with reference to FIGS.4-8.

Process 300 may include monitoring conditions corresponding to policytriggers (block 320). For instance, IoT tracker 220 may collectinformation that corresponds to conditions or triggers associated withthe battery conservation policy. Examples of such information mayinclude a distance between a particular user device 210 (that ismonitoring the location of IoT tracker 220) and the IoT tracker 220itself, a current date and time that corresponds to a scheduled date andtime for implementing a battery conservation mode, a location of IoTtracker 220 (e.g., with reference to a geographic area and/or boundary).Additional examples are discussed below with reference to FIGS. 4-8.

Process 300 may include determining that the monitored conditions havesatisfied the policy trigger (block 330). For example, IoT tracker 220may compare the monitored conditions to the policy trigger, defined bythe battery conservation policy, and determine that the monitoredconditions have satisfied the policy trigger. For instance, if thepolicy trigger is that IoT tracker 220 is not to leave a particulargeographic area then IoT tracker 220 may determine that the policytrigger is satisfied upon detecting that IoT tracker 220 has left theparticular geographic area. As another example, if the policy trigger isthat IoT tracker 220 may enter a battery conservation mode when the IoTtracker 220 is no longer moving, IoT tracker 220 may determine that thepolicy trigger is satisfied upon detecting accelerometer readings thatare below a threshold level of accelerometer activity. Additionalexamples are discussed below with reference to FIGS. 4-8.

Process 300 may include implementing a battery conservation mode that isassociated with the battery conservation policy (block 340). Forexample, IoT tracker 220 may enter into a battery conservation modeassociated with the battery conservation policy. In implementations,where the battery conservation policy includes different policy triggersthat can trigger different battery conservation modes (one mode being asleep mode and the other mode being a PSM), IoT tracker 220 may enterinto a battery conservation mode associate with a particular (i.e.,whichever) policy trigger that was satisfied by the monitoredconditions. IoT tracker 220 may communicate its entry into a particularbattery conservation mode to the network as noted above. In someimplementations, IoT tracker 220 may communicate its entry into abattery conservation mode to a user device 210 that is associated withIoT tracker 220. For example, IoT tracker 220 may communicate that ithas entered a battery conservation mode, the type of batteryconservation mode, and/or the trigger that caused the entry to batteryconservation mode. The communication may be to the user device 210directly (e.g., via the networking facilities of FIG. 2) or throughcommunication with the IoT tracker services system 260.

In some implementations, prior to entering into a power conservationmode, IoT tracker 220 may communicate with user device 210 in order tohave the user of user device 210 confirm whether IoT tracker 220 mayenter into the power conservation mode. If IoT tracker 220 receives suchconfirmation, IoT tracker 220 may proceed by entering into the powerconservation mode. If IoT tracker 220 does not receive such aconfirmation, IoT tracker 220 may refrain from entering into the powerconservation mode (e.g., for a period of time).

FIG. 4 illustrates an example of instructions and information that maybe included in a battery conservation policy. As shown, a batteryconservation policy may include trigger conditions, data collection andprocessing instructions, triggers or threshold conditions, batteryconservation modes, and battery conservation parameters. In someimplementations, a battery conservation policy may include fewerinstructions and/or information; different instructions and/orinformation; or differently arranged instructions and/or informationthan what is illustrated in FIG. 4. The scope of the techniquesdescribed herein may also include battery conservation policies that arecomplex and may include multiple conditions, thresholds and triggers,different battery conservation modes, various battery conservationparameters, etc.

Trigger conditions may include a condition or set of conditions that maycause IoT tracker 220 to enter into a battery conservation modeassociated with that condition or set of conditions. Examples of triggerconditions may include proximity-based conditions, schedule-basedconditions, user-initiated location reporting, geo-fencing conditions,activity-based conditions, and more.

Proximity-based conditions may include a geographic distance between acurrent location of a user device 210 that is monitoring the location ofIoT tracker 220 and the current location of the IoT tracker 220 itself.For instance, if IoT tracker 220 is attached to a dog collar, in orderto enable an owner of the dog to use his or her user device 210 to trackthe current location of the dog, the trigger condition may be aparticular distance (e.g., 15 feet) between the IoT tracker 220 on thedog and the user device 210 of the owner. As such, if/when the owner iswithin 15 feet of the dog, IoT tracker 220 may enter into a batteryconservation mode (e.g., a sleep mode, a PSM, etc.) in order to conservethe battery power of IoT tracker 220. The notion behind such a triggercondition may be that if the owner is within 15 feet of the dog, theowner should know (e.g., be able to see) the physical location of thedog and, therefore, there is no need for the IoT tracker 220 to wastethe battery power that would be required to notify the owner of thelocation of the dog.

Scheduled-based conditions may include scenarios in which the locationof a particular IoT tracker 220 may be assumed because of a scheduleassociated with the particular IoT tracker 220. For example, a parentmay attach IoT tracker 220 to a backpack of his or her child, and maycreate a battery conservation policy for IoT tracker 220 that takesadvantage of the known school schedule of the child. If the parentalready knows that the child will be at school from 9:00 AM to 3:00 PMfrom Monday to Friday, a trigger condition may be created to cause IoTtracker 220 to enter into a battery conservation mode from Monday toFridays between the hours of 9:00 AM and 3:00 PM.

User-initiated location reporting may include a trigger condition thatmay cause IoT tracker 220 to actually discontinue a battery conservationmode. For example, a hiker may embark on an extended hike that does notrequire him or her to transmit their current location on a frequentbasis. Because of the remoteness of his or her location, transmission oftheir location may require considerable battery power. As a result, itmay be advantageous to have the IoT tracker 220 default to a batteryconservation mode, such that the IoT tracker 220 may only transmitlocation information upon a specific command from the user to do so.

Geo-fencing may include designating geographic areas as triggerconditions for entering into (or exiting out of) battery conservationmodes. For example, a parent may place an IoT tracker 220 in a pantpocket of his or her child and allow the child to play in a yard, aneighborhood, or another geographic area defined by the parent. In sucha scenario, so long as the child (i.e., the IoT tracker 220) remainswithin the designated area, the IoT tracker 220 may remain in a batteryconservation mode (e.g., a sleep mode). If/when, however, the childleaves the designated area, the IoT tracker 220 may exit the batteryconservation mode and begin transmitting the geographic location of thechild. If the child were to return to the designated area, the IoTtracker 220 may once again enter into a battery conservation mode. Inthis manner, geographic boundaries may be designated as triggerconditions for causing IoT tracker 220 to enter into, or exit out of, abattery conservation mode.

An activity-based trigger-condition may be based on whether IoT tracker220 is moving. For instance, an IoT tracker 220 that is placed on avehicle may monitor (e.g., via an accelerometer or another device of IoTtracker 220) if/when IoT tracker 220 is in motion. So long as thevehicle is in motion, IoT tracker 220 may transmit the movements of IoTtracker 220. However, if/when the vehicle stops, IoT tracker 220 mayenter into a battery conservation mode since there may be no need totrack the movements of a vehicle that isn't move.

Data collection and processing may include instructions about what typesof information should be collected and/or how such information should beprocessed in order to properly implement a particular batteryconservation policy. In some implementations, such instructions maydepend on the trigger conditions that are defined for the batteryconservation policy and/or whether IoT tracker 220 is currentlyimplementing a battery conservation mode. For example, the datacollection and processing instructions for a schedule-based triggercondition may monitor a current date and time and whether the currentdate and time bears any significance on a schedule designated for IoTtracker 220. As another example, the data collection and processinginstructions for a proximity-based trigger condition may includereceiving a location of UE 210, determining a location of IoT tracker220, and determining a distance between user device 210 and IoT tracker220. In another example, the data collection and processing instructionsfor a geo-fencing trigger condition may include monitoring the currentlocation of Iot tracker 220 and determining whether the current locationis inside of, or outside of, a designated geographic area. As such, datacollection and processing may include instructions about what types ofinformation should be collected and/or how such information should beprocessed in order to properly implement a particular batteryconservation policy.

Trigger or threshold information may include a description of acondition that may cause IoT tracker 220 to enter into a batteryconservation mode (or to discontinue a battery conservation mode). Forexample, the threshold information for a proximity-based triggercondition may include a distance (e.g., 10 feet). When the distancebetween user device 210 and IoT tracker 220 is less than (or equal to)10 feet, IoT tracker 220 may initiate a battery conservation mode;however, if/when the distance between user device 210 and IoT tracker220 is greater than 10 feet, IoT tracker 220 may discontinue the batteryconservation mode. As another example, if the trigger condition is anactivity-based condition trigger, the threshold information may includea change acceleration that is greater than a threshold level ofacceleration. For example, if IoT tracker 220 is attached to a child'sbackpack, the backpack may remain stationary while the child is atschool; however, once school is over, the child may tend to leave theschool with the backpack, which will register a change in accelerationthat is above an acceleration threshold indicative of movement.

A battery conservation mode may include rules and instructions that aredesigned to limit the amount of battery power being used by IoT tracker220. As mentioned above, examples of battery conservation modes mayinclude a sleep mode (e.g., eDRX) and a PSM. In some implementations,certain battery conservation modes may be more suitable for certaintrigger conditions. For example, a sleep mode may be more suitable forgeo-fencing type scenario because using a sleep mode may cause IoTtracker 220 to periodically check whether or not the IoT tracker 220 hascrossed the geo-fence. By contrast, PSM may be advantageous for ascenario involving an activity-based trigger because, even while IoTtracker 220 is in a PSM, IoT tracker 220 may continue to receive inputfrom an accelerometer of IoT tracker 220.

Battery conservation parameters may include details about implementing aparticular battery conservation mode. For example, battery conservationparameters may include information about how long to stay in a PSM(e.g., during a schedule-based trigger condition, an activity basedtrigger condition, etc.). Another example may include how much time(e.g., in sleep mode, eDRX mode, etc.) should IoT tracker 220 waitbefore checking with the network about available information, what typesof information from the network is important enough (e.g., IoT tracker220 an updated battery conservation policy) to cause IoT tracker 220 towake up from a sleep mode, etc.

FIG. 5 illustrates an example for implementing a proximity-based batteryconservation policy. As shown, the example of FIG. 5 may include userdevice 210, IoT tracker 220, eNB 230, network 240, and IoT trackerservices device 260. Descriptions of the devices and networks of FIG. 5are provided above with reference to FIG. 2. For the purposes ofexplaining the example of FIG. 5, assume IoT tracker 220 is installed inthe vehicle depicted in FIG. 5, and that the user of user device 210 isthe owner of the vehicle.

A proximity-based conservation policy may include a conditions triggerthat is based on a distance between user device 210 and IoT tracker 220.When the distance between user device 210 and IoT tracker 220 is greaterthan a pre-selected threshold, IoT tracker 220 may remain in an activemode by periodically transmitting the geographic location of IoT tracker220 (and therefore the vehicle) to eNB 230. By contrast, when thedistance between user device 210 and IoT tracker 220 is less than (orequal to) a pre-selected threshold, IoT tracker 220 may enter into abattery conservation mode (e.g., a sleep mode or a PSM). As such, whenthe driver is far away from his or her vehicle, the driver may use thelocation services and capabilities of user device 210 and IoT tracker220 in order to locate his or her vehicle. However, once the driver iswithin the pre-selected threshold distance, the driver may be able tosee his or her vehicle and, therefore, no longer require the assistanceof user device 210 and/or IoT tracker 220.

The distance between user device 210 and IoT tracker 220 may bedetermined in a variety of ways. In one implementation, user device 210and IoT tracker 220 may each determine their respective locations andtransmit their locations to a network device, (such as eNB 230 or IoTtracker services system 260), and the network device may calculate thedistance between user device 210 and IoT tracker 220 and provide thedistance to IoT tracker 220. In some implementations, IoT tracker 220may determine a location of IoT tracker 220, obtain the location of userdevice 210 from the network (e.g., eNB 230, IoT tracker services system260, etc.), and calculate the distance between user device 210 and IoTtracker 220. In some implementations, user device 210 may obtain thelocation information of user device 210 and IoT tracker 220, calculatethe distance there between, and provide the distance to IoT tracker 220.In yet other implementations, IoT tracker 220 may use a low powerbeacon, such as Bluetooth Low Energy (BTLE) mode, to determine theproximity of user device 210. In such implementations, when user device210 is detected, IoT tracker 220 may enter into a battery conservationmode.

FIG. 6 illustrates an example schedule that may be used to implement aschedule-based battery conservation policy. As described above, a userof user device 210 (or another type of UE) may communicate with IoTtracker services device 260 to create the schedule, and IoT trackerservices device 260 may provide the schedule to IoT tracker 220. In someimplementations, the user may instead communicate, via user device 210,directly with IoT tracker 220 to create the schedule.

As shown, the example schedule includes a Day column, a Time column, aLocation column, and a Mode column. Each cell in the Day column mayinclude a day of the week, each cell in the Time column may include atime period (e.g., 9 AM-3 PM), and each cell in the Location column mayinclude a geographic area. Additionally, each cell in the Mode columnmay include a type of battery conservation mode, such as a sleep mode orPSM. The example schedule of FIG. 6 is only one representation of thetypes of information that may be included in a scheduled-based batteryconservation policy. In another implementation, a scheduled-basedbattery conservation policy may include additional information, fewerinformation, different information, or differently arranged information.

For purposes of explaining FIG. 6, assume that the example scheduleincludes a weekly schedule of a teenager that attends high school, has apart-time job, and regularly attends some type of religious service. Assuch, IoT tracker 220 may enter into a PSM on Monday through Friday,between 9:00 AM and 3:00 PM, because the teenager is at school. OnWednesdays, between 5:00 PM and 10:00 PM the teenager is at work, so IoTtracker 220 may enter into a sleep mode. On Sundays between 9:00 AM and10:00 PM, IoT tracker 220 may enter a sleep mode because the teenager isin church. As such, scheduling information may be used to implement abattery conservation policy.

In the foregoing description the cells in the Location column were meredescriptions of the teenager's locations at the corresponding days andtimes. In some implementations, however, the cells in the Locationcolumn may instead be requirements (e.g., trigger conditions) of thebattery conservation policy. For instance, IoT tracker 220 may onlyenter PSM on Mondays between 9:00 AM and 3:00 PM, so long as theteenager is located at school. Similarly, IoT tracker 220 may only entera sleep mode on Wednesdays, between 5:00 PM and 10:00 PM, so long as theteenager is located at work. If the teenager leaves school between thehours of 9:00 AM and 3:00 PM on Monday (or leaves work between the hoursof 5:00 PM and 10:00 PM on Wednesday), IoT tracker 220 may exit the PSM(or the sleep mode) and resume tracking the locations of the teenageruntil, for example, the teenager returns to where the schedule indicatesthat he or she should be. In this manner, different types of conditions(e.g., schedule conditions and geographic location conditions) may becoupled together to create more complex trigger condition for a batteryconservation policy.

FIG. 7 illustrates an example of using geo-fencing to implement abattery conservation policy. The example of FIG. 7 depicts a communitythat includes a park, a restaurant, a shopping center, a gas station, aschool, and a neighborhood that includes a home, a friend's home, andtwo houses. The example of FIG. 7 also includes two geo-fences, onearound the school and another around the home and the friend's home. Forpurposes of explaining FIG. 7, assume that a parent is using a userdevice 210 to track the geographic location and movements of his or herchild via an IoT tracker 220.

As described above, the parent of user device 210 may have created abattery conservation policy for IoT tracker 220, which includes the twogeo-fences depicted in FIG. 7. As such, IoT tracker 220 may transmit thelocation of the child so long as the child does not enter the areasdefined by the two geo-fences (i.e., the school or the home and/orfriend's home). If the child enters the school, is at home, or is at hisor her friend's home, IoT tracker 220 may enter into a batteryconservation mode, such as a sleep mode or a PSM, and may not transmitthe current location of the child. However, if/when the child leavesthose areas, IoT tracker 220 may resume transmitting the location of thechild. In some implementations, since the parent may consider theschool, the home, and the friend's home to be safe locations for thechild, the parent may not need to know the exact location of the childso long as he or she is at one of those locations. However, once thechild leaves one of those locations, the user device 210 of the parentmay once again begin to receive the current geographic location of IOTtracker 220 (i.e., the child).

FIG. 8 illustrates an example of an activity-based battery conservationpolicy. As shown, the example of FIG. 8 includes a timeline extendingfrom a left-most portion of FIG. 8 to a right-most portion of FIG. 8.The example also includes a vehicle with an IoT tracker 220 installedtherein. For purposes of FIG. 8, assume that IoT tracker 220 is not ableto use a battery of the vehicle, but instead is using a battery of IoTtracker 220.

As shown, a vehicle may be in an active state (e.g., being driven fromone location to another). IoT tracker 220 may determine that the vehicleis in motion in one or more ways, such as by inputs from anaccelerometer of IoT tracker 220, by a vehicle control system of thevehicle informing IoT tracker 220 that the vehicle is moving, etc. Asdepicted, so long as the vehicle is in motion, IoT tracker 220 may be inan active state (i.e., periodically determining and transmitting thelocation of IoT tracker 220). At some point, the vehicle may stop, andin response, IoT tracker 220 may initiate a timer. The timer may be longenough for IoT tracker 220 to verify that the vehicle has not merelystopped at a stop sign, a traffic light, etc., but that the vehicle hasstopped for what appears will be an extended duration.

Upon expiration of the timer, IoT tracker 220 may enter into a batteryconservation mode in order to help preserve the amount of power in thebattery of IoT tracker 220. During this time, however, IoT tracker 220may continue to monitor certain conditions. For example, IoT tracker 220may continue to monitor an input from an accelerometer of IoT tracker220. As such, when the vehicle starts to move, IoT tracker 220 maydetect that the vehicle is once again moving due to an input from anaccelerometer of IoT tracker 220. In response, IoT tracker 220 may exitthe battery conservation mode and resume determining a location of IoTtracker 220 and transmitting the location to the network.

FIG. 9 illustrates an example process 900 for generating a batteryconservation policy. In some implementations, process 900 may beimplemented by IoT tracker 220.

Process 900 may include gathering information relevant to battery usage(block 910). For example, IoT tracker 220 may gather information thatmay be relevant to predicting times and places when IoT tracker 220 maybenefit from a battery conservation mode. Examples of such informationmay include historical information relating to patterns, schedules,times, and locations that IoT tracker 220 tends to experience. Forinstance, IoT tracker 220 may record time, date, and locationinformation over the course of the month, which may include an emphasison times, dates, and locations where IoT tracker 220 appears to havebeen stationary. In some implementations, the gathered information mayinclude other types of information as well. Examples of such informationmay include future plans or scheduling information about meetings,classes, airline travel, etc., also with an emphasis on times, dates,and locations where IoT tracker 220 will likely be stationary. Asdescribed below, the information gathered by IoT tracker 220 may be usedto determine whether a battery conservation mode may be beneficial atcertain times, for certain locations, etc.

Process 900 may include determining, based on the gathered information,whether a battery conservation policy would be beneficial (block 920).For instance, IoT tracker 220 may analyze the information in order toidentify behavioral patterns (or future plans) where IoT tracker 220might benefit from a battery conservation policy. In one example, byanalyzing the information, IoT tracker 220 may determine that the IoTtracker 220 is scheduled to be at a particular location (e.g., a school)every Monday from 12:00 PM to 3:00 PM, and since the IoT tracker 220likely would not be moving much during that time, the IoT tracker 220may conclude that entering into a battery conservation mode during thattime would be beneficial.

Process 900 may include generating a battery conservation policy andobtaining approval thereof from a user (block 910). For example, IoTtracker 220 may create a battery conservation policy based on when IoTtracker 220 would likely benefit from implementing a batteryconservation policy. Generating a battery conservation policy mayinclude creating rules, defining triggers and trigger conditions,selecting battery conservation modes, etc. To continue with the exampleprovided above, IoT tracker 220 may generate a battery conservationpolicy that would cause the IoT tracker 220 to enter into a batteryconservation mode between 12:00 PM and 3:00 PM each Monday. In someimplementations, the battery conservation policy may require aprerequisite, such as confirming that IoT tracker 220 is actuallylocated at the school. IoT tracker 220 may also, or alternatively,notify a user (e.g., of a UE 210 registered to track the location of theIoT tracker 220) regarding the plan. Doing so may, for example, providethe user with an opportunity to accept or reject the proposed policy.

Process 900 may include implementing a battery conservation proposal inresponse to an approval thereof. For example, IoT tracker 220 mayreceive an indication, from the user, that the battery conservationpolicy has been approved. In response to the approval of the policy, IoTtracker 220 may implement the policy. For instance, once the IoT tracker220 is located at the school on Monday at 12:00 PM, the IoT tracker 220may entering into a battery conservation mode in accordance with thebattery conservation policy.

FIG. 10 is a diagram of example components of a device 1000. Each of thedevices illustrated in FIGS. 1, 2, 5, 7, and 8 may include one or moredevices 1000. Device 1000 may include bus 1010, processor 1020, memory1030, input component 1040, output component 1050, and communicationinterface 1060. In another implementation, device 1000 may includeadditional, fewer, different, or differently arranged components. Asdescribed herein, a component may be implemented by hardware circuitry,software logic, and/or some combination thereof. Additionally,circuitry, as described herein, may be implemented by hardware, softwarelogic, and/or some combination thereof

Bus 1010 may include one or more communication paths that permitcommunication among the components of device 1000. Processor 1020 mayinclude a processor, microprocessor, or processing logic that mayinterpret and execute instructions. Memory 1030 may include any type ofdynamic storage device that may store information and instructions forexecution by processor 1020, and/or any type of non-volatile storagedevice that may store information for use by processor 1020.

Input component 1040 may include a mechanism that permits an operator toinput information to device 1000, such as a keyboard, a keypad, abutton, a switch, etc. Output component 1050 may include a mechanismthat outputs information to the operator, such as a display, a speaker,one or more light emitting diodes (LEDs), etc.

Communication interface 1060 may include any transceiver-like mechanismthat enables device 1000 to communicate with other devices and/orsystems. For example, communication interface 1060 may include anEthernet interface, an optical interface, a coaxial interface, or thelike. Communication interface 1060 may include a wireless communicationdevice, such as an infrared (IR) receiver, a cellular radio, a Bluetoothradio, or the like. The wireless communication device may be coupled toan external device, such as a remote control, a wireless keyboard, amobile telephone, etc. In some embodiments, device 1000 may include morethan one communication interface 1060. For instance, device 1000 mayinclude an optical interface and an Ethernet interface.

Device 1000 may perform certain operations described above. Device 1000may perform these operations in response to processor 1020 executingsoftware instructions stored in a computer-readable medium, such asmemory 1030. A computer-readable medium may be defined as anon-transitory memory device. A memory device may include space within asingle physical memory device or spread across multiple physical memorydevices. The software instructions may be read into memory 1030 fromanother computer-readable medium or from another device. The softwareinstructions stored in memory 1030 may cause processor 1320 to performprocesses described herein. Alternatively, hardwired circuitry may beused in place of or in combination with software instructions toimplement processes described herein. Thus, implementations describedherein are not limited to any specific combination of hardware circuitryand software.

In the preceding specification, various preferred embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope set forth in the claims that follow. The specificationand drawings are accordingly to be regarded in an illustrative ratherthan restrictive sense.

For example, while a series of lines, arrows, and/or blocks have beendescribed with regard to FIGS. 1, 3, 4, and 9 the order of the blocksand arrangement of the lines and/or arrows may be modified in otherimplementations. Further, non-dependent blocks may be performed inparallel. Similarly, while series of communications have been describedwith regard to several of the Figures provided herein, the order ornature of the communications may potentially be modified in otherimplementations.

It will be apparent that example aspects, as described above, may beimplemented in many different forms of software, firmware, and hardwarein the implementations illustrated in the figures. The actual softwarecode or specialized control hardware used to implement these aspectsshould not be construed as limiting. Thus, the operations and behaviorsof the aspects that were described without reference to the specificsoftware code—it being understood that software and control hardwarecould be designed to implement the aspects based on the descriptionherein.

Further, certain portions may be implemented as “logic” that performsone or more functions. This logic may include hardware, such as anapplication-specific integrated circuit (ASIC) or a field-programmablegate array (FPGA), or a combination of hardware and software.

To the extent the aforementioned embodiments collect, store or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection” of personal information. Additionally, thecollection, storage and use of such information may be subject toconsent of the individual to such activity, for example, throughwell-known “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to be limiting. In fact, many of these features may be combinedin ways not specifically recited in the claims and/or disclosed in thespecification.

No element, act, or instruction used in the present application shouldbe construed as critical or essential unless explicitly described assuch. An instance of the use of the term “and,” as used herein, does notnecessarily preclude the interpretation that the phrase “and/or” wasintended in that instance. Similarly, an instance of the use of the term“or,” as used herein, does not necessarily preclude the interpretationthat the phrase “and/or” was intended in that instance. Also, as usedherein, the article “a” is intended to include one or more items, andmay be used interchangeably with the phrase “one or more.” Where onlyone item is intended, the terms “one,” “single,” “only,” or similarlanguage is used. Further, the phrase “based on” is intended to mean“based, at least in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: one or more processorsconfigured to: monitor a proximity of the device to a particular UserEquipment (“UE”); determine, based on the monitoring, that a firstproximity of the device to the particular UE exceeds a thresholdproximity; based on determining that the first proximity exceeds thethreshold proximity, monitor a geographical location of the device;subsequently determine, based on further monitoring of the proximity tothe particular UE or based on the monitoring of the geographicallocation of the device, that a second proximity to the particular UEdoes not exceed the threshold proximity; and based on the subsequentdetermination that the second proximity to the particular UE does notexceed the threshold proximity, cease monitoring the geographicallocation of the device.
 2. The device of claim 1, wherein ceasingmonitoring the geographical location of the device includes entering apower conservation mode.
 3. The device of claim 2, wherein the one ormore processors are further configured to: exit the power conservationmode after entering the power conservation mode, wherein exiting thepower conservation mode includes further continuing to monitor thegeographical location of the device.
 4. The device of claim 2, whereinthe power conservation mode is a first power conservation mode, whereinthe one or more processors are further configured to: exit the firstpower conservation mode after entering the first power conservationmode; determine, after exiting the first power conservation mode, that aparticular trigger condition has been met; and based on determining thatthe particular trigger condition has been met, enter a second powerconservation mode that is different from the first power conservationmode.
 5. The device of claim 4, wherein the second power conservationmode includes a particular interval at which the device monitors ageographical location of the device.
 6. The device of claim 1, whereinceasing to monitor the geographical location of the device consumes lessbattery power of the device than monitoring, by the device, thegeographical location of the device.
 7. The device of claim 1, whereinceasing monitoring the geographical location of the device includesentering a power conservation mode, wherein the one or more processorsare further configured to: exit the power conservation mode afterentering the power conservation mode, wherein exiting the powerconservation mode includes further continuing to monitor thegeographical location of the device; determine, after exiting the powerconservation mode, that a measure of acceleration associated with thedevice is below a threshold measure of acceleration; and enter the powerconservation mode based on determining that the measure of accelerationassociated with the device is below the threshold measure ofacceleration.
 8. A non-transitory computer-readable medium, storing aplurality of processor-executable instructions to: monitor a proximityof a device to a particular User Equipment (“UE”); determine, based onthe monitoring, that a first proximity of the device to the particularUE exceeds a threshold proximity; based on determining that the firstproximity exceeds the threshold proximity, cause the device to monitor ageographical location of the device; subsequently determine, based onfurther monitoring of the proximity to the particular UE or based on themonitoring of the geographical location of the device, that a secondproximity to the particular UE does not exceed the threshold proximity;and based on the subsequent determination that the second proximity tothe particular UE does not exceed the threshold proximity, cause thedevice to cease monitoring the geographical location of the device. 9.The non-transitory computer-readable medium of claim 8, wherein ceasingmonitoring the geographical location of the device includes entering apower conservation mode.
 10. The non-transitory computer-readable mediumof claim 9, wherein the plurality of processor-executable instructionsfurther include processor-executable instructions to: cause the deviceto exit the power conservation mode after entering the powerconservation mode, wherein exiting the power conservation mode includesfurther continuing to monitor the geographical location of the device.11. The non-transitory computer-readable medium of claim 9, wherein thepower conservation mode is a first power conservation mode, wherein theplurality of processor-executable instructions further includeprocessor-executable instructions to: exit the first power conservationmode after entering the first power conservation mode; determine, afterthe device exits the first power conservation mode, that a particulartrigger condition has been met; and based on determining that theparticular trigger condition has been met, cause the device enter asecond power conservation mode that is different from the first powerconservation mode.
 12. The non-transitory computer-readable medium ofclaim 11, wherein the second power conservation mode includes aparticular interval at which the device monitors a geographical locationof the device.
 13. The non-transitory computer-readable medium of claim8, wherein ceasing to monitor the geographical location of the deviceconsumes less battery power of the device than monitoring, by thedevice, the geographical location of the device.
 14. The non-transitorycomputer-readable medium of claim 8, wherein ceasing monitoring thegeographical location of the device includes entering a powerconservation mode, wherein the plurality of processor-executableinstructions further include processor-executable instructions to: causethe device to exit the power conservation mode after entering the powerconservation mode, wherein exiting the power conservation mode includesfurther continuing to monitor the geographical location of the device;determine, after exiting the power conservation mode, that a measure ofacceleration associated with the device is below a threshold measure ofacceleration; and cause the device to enter the power conservation modebased on determining that the measure of acceleration associated withthe device is below the threshold measure of acceleration.
 15. A method,comprising: monitoring a proximity of a device to a particular UserEquipment (“UE”); determining, based on the monitoring, that a firstproximity of the device to the particular UE exceeds a thresholdproximity; based on determining that the first proximity exceeds thethreshold proximity, monitoring a geographical location of the device;subsequently determining, based on further monitoring of the proximityto the particular UE or based on the monitoring of the geographicallocation of the device, that a second proximity to the particular UEdoes not exceed the threshold proximity; and based on the subsequentdetermination that the second proximity to the particular UE does notexceed the threshold proximity, ceasing monitoring the geographicallocation of the device.
 16. The method of claim 15, wherein ceasingmonitoring the geographical location of the device includes entering apower conservation mode.
 17. The method of claim 16, further comprising:exiting the power conservation mode after entering the powerconservation mode, wherein exiting the power conservation mode includesfurther continuing to monitor the geographical location of the device.18. The method of claim 16, wherein the power conservation mode is afirst power conservation mode, the method further comprising: exitingthe first power conservation mode after entering the first powerconservation mode; determining, after exiting the first powerconservation mode, that a particular trigger condition has been met; andbased on determining that the particular trigger condition has been met,entering a second power conservation mode that is different from thefirst power conservation mode, wherein the second power conservationmode includes a particular interval at which the device monitors ageographical location of the device.
 19. The method of claim 15, whereinceasing to monitor the geographical location of the device consumes lessbattery power of the device than monitoring the geographical location ofthe device.
 20. The method of claim 15, wherein ceasing monitoring thegeographical location of the device includes entering a powerconservation mode, the method further comprising: exiting the powerconservation mode after entering the power conservation mode, whereinexiting the power conservation mode includes further continuing tomonitor the geographical location of the device; determining, afterexiting the power conservation mode, that a measure of accelerationassociated with the device is below a threshold measure of acceleration;and entering the power conservation mode based on determining that themeasure of acceleration associated with the device is below thethreshold measure of acceleration.